ASCE™ - Known Issues with ASCE 3.5

Contents

• Error message on exit
• Creating links to local files: "File not found"
• Checking links in the node editor: "Object doesn't support this property or method", or "Object already loaded"
• Unable to re-open file: "File does not have the required structure"
• Unable to edit status fields or table view "Object variable or With block variable not set" or "Type mismatch"

Error message on exit

Description:

Having closed a file at the end of a work session, and having exited ASCE, an error message appears indicating that ASCE has not been closed down properly.

Status:

This is a known issue with ASCE versions 3.5.10, 3.5.14 and 3.0.15.

Explanation:

This problem is caused by a third party library used to implement an ASCE component (namely, the Table View). A fix is available as part of the 2nd maintenance release for ASCE.

Fix:

Install the 2nd maintenance release for ASCE.

Link to local files: "File not found error"

Description:

In the node text editor, the user creates a link to a local file. When the node editor is closed and re-opened, the link is no longer valid: the user clicks on the file link and then on the "Verify" or "View" buttons. The message "file not found appears". Alternatively, when choosing Tools → Check Embedded Links in the main menu, followed by clicking the Check Links button, the linked file in question shows up as "[your file] does not exist".

Status:

This is a known issue with versions of ASCE 3.5 up to 3.5.30

Explanation:

When node text is saved, the underlying HTML is "tidied" to remove redundant markup. A configuration error means that during this process double spaces in the names of linked files are compressed to a single space. The version of the file name stored in ASCE now no longer matches that of the original file, with the result that ASCE can no longer correctly find the file.

Fix:

1. Locate the folder where ASCE is installed. Show me how to do this.
2. Open the folder "tidy-filters"
3. Use Windows Notepad or a similar, simple text editor to open the file "sanity-check.tidy".
4. Insert the line:
   literal-attributes: yes
5. Save and close the file. I get an error when I try and save.
6. Restart ASCE
7. Locate your broken links:
   1. Tools → Check Embedded Links
   2. Click the Check Links button
   3. Double-click on each of the links to files that are reported as not existing. This will open the node editor and locate the broken links.
   4. Click on the link and repair it by using the Browse button to locate the intended linked file
   5. Click the Update button to save the link
   6. Close and save the node editor
   7. Repeat steps C-F for each broken link

Error while checking links to other nodes

Status:

This is a known issue with versions of ASCE 3.5 up to 3.5.30

Description:

To check links to other nodes in the node editor, the user clicks on a link. One of the following error messages appears:

    error-details: [
        application-name: {Assurance and Safety Case Environment (ASCE)}
        application-version: 3.5.30
        windows-version: {Windows NT version: 5.1 (Build 2600: Service Pack 2)}
        error-num: 438 error-description: {Object doesn't support this property
        or method} error-source: {ASCE} function-name: {dhtmleditmain_onclick}
        line-number: 6500 call-stack: [
            [function-name: {dhtmleditmain_onclick} line-number: 6500]
            [function-name: {showlinkingform} line-number: 10296]
            [function-name: {htmlelement} line-number: 18663]
        ]
    ]
    

    error-details: [
        application-name: {Assurance and Safety Case Environment (ASCE)}
        application-version: 3.5.30
        windows-version: {Windows NT version: 5.1 (Build 2600: Service Pack 2)}
        error-num: 360 error-description: {Object already loaded} error-source:
        {ASCE} function-name: {dhtmleditmain_onclick} line-number: 6500
        call-stack: [
            [function-name: {dhtmleditmain_onclick} line-number: 6500]
            [function-name: {showlinkingform} line-number: 10296]
            [function-name: {htmlelement} line-number: 18658]
       ]
    ]
    

Explanation:

This error occurs if the user clicks on the link with the left and right mouse buttons simultaneously or near-simultaneously. ASCE mistakenly interprets these clicks as two conflicting messages.

Fix:

• Click on links using the left mouse button only.
• If the error does occur, click the "Next" button, then choose "ignore and continue".

Unable to re-open file. Error: "File does not have the required structure in OpenASCENetworkDialog"

Status:

This is a known issue with versions of ASCE 3.5 up to 3.5.30

Description:

When opening a previously edited ASCE file, the message "File does not have the required structure in OpenASCENetworkDialog" appears, and the file cannot be opened. Another early symptom may be that user view images, when embedded into the node text, do not display, leaving in their place a small red "broken image" icon.

Explanation:

User view images have become corrupted. ASCE is unable to process these when it opens the file.

Fix:

Whilst the user view images may become corrupted, the user views themselves (namely the choice and layout of the node on the user view window) are likely to be intact. It is therefore possible to remove the corrupt image data and ASCE can then correctly regenerate the image date. To remove the corrupt image data

• Send your ASCE .axml file to asce_support(at)adelard.com: we can quickly repair and return the file
• Alternatively, perhaps if there are confidentiality issues, repair the file yourself. Contact us at asce_support(at)adelard.com for instructions and advice.

Unable to edit status fields or use table view

Status:

This is a known issue with ASCE 3.5.15

Description

An error is seen when editing the status fields of some nodes, or when opening the table view.

This is typical of the error seen when editing status fields of such a node:

	error-details: [
	   application-name: {Assurance and Safety Case Environment (ASCE)}
	   application-version: 3.5.15
	   windows-version: {Windows NT version: 5.1 (Build 2600: Service Pack 2)}
	   error-num: 91
	   error-description: {Object variable or With block variable not set}
	   error-source: {ASCE}
	   function-name: {mnuUserStatusFields_Click}
	   line-number: 33685
	   call-stack: [
		  [function-name: {mnuUserStatusFields_Click} line-number: 33685]
		  [function-name: {NodeKey} line-number: 18929]
		  [function-name: {FetchNodeData} line-number: 19147]
		  [function-name: {GetNodeStatusValueFromDOM} line-number: 45888]
		  ]
	
	]

This is typical of the error seen going within Table View:

	error-details: [
		application-name: {Assurance and Safety Case Environment 
		(ASCE)}
		application-version: 3.5.15
		windows-version: {Windows NT version: 5.1 (Build 2600: Service 
		Pack 2)}
		error-num: 13
		error-description: {Type mismatch}
		error-source: {ASCE}
		function-name: {Form_Load}
		line-number: 23209
		call-stack: [
			[function-name: {Form_Load} line-number: 23209]
			[function-name: {PopulateGrid} line-number: 23026]
			[function-name: {GetNodeStatusValueFromDOM} line-number: 45895]
			[function-name: {SafeCBool} line-number: 43541]
		]
	]

Explanation

The bug arises when the following characters have been entered into the status fields: "<", ">" or "&"

Fix

It is necessary to remove the characters "<", ">" and "&" from the status fields. There are a number of options

• Send your ASCE .axml file to asce_support(at)adelard.com: we can quickly repair and return the file
• Alternatively, perhaps if there are confidentiality issues, repair the file yourself. Contact us at asce_support(at)adelard.com for instructions and advice.

Once fixed, download 2nd maintenance release of ASCE 3.5, which includes a fix for this bug

If you cannot update your version of ASCE, you will need to avoid these characters in the node status fields. For example, use "and" instead of "&"